-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Procedures #619
feat: Procedures #619
Conversation
/ok-to-test sha=6b08ca9 |
Integration tests success for 6b08ca9 |
@funes79 Can you also run the |
@ChrisIsidora docs and examples added. |
@alldoami is it ok to merge? |
/ok-to-test sha=a736b4d |
If you run |
Integration tests failure for a736b4d |
I do not understand. On my local |
Yes I got a diff, so now I pushed a new commit to update the docs for procedure. |
@funes79 I don't know exactly why but I had similar issues some time ago when I also introduced a new resources. I suspect that the So fastest solution for now is to remove the new .md and after the merge, open a PR with only the new .md. (Related to #632) |
/ok-to-test sha=40aca4d |
Integration tests success for 40aca4d |
Test Plan
References